---

This section details on the original issue you should resolve

<issue_title>Add type-safe Tailwind CSS support with conflict detection</issue_title>
<issue_description>## Problem

Using Tailwind CSS classes as raw strings (class("px-4 text-center")) provides no safety — conflicting classes like px-4 and px-2 on the same element are silently accepted, leading to unpredictable styling.

Proposed Design

Create an ironhtml-tailwind crate that provides:

1. Typed class enums

Each Tailwind utility category is an enum, preventing conflicts at the type level:

use ironhtml_tailwind::{Padding, TextAlign, Display, FontWeight};

// Each category can only be set once per element
element
    .tw(Padding::X(4))       // px-4
    .tw(TextAlign::Center)   // text-center
    .tw(Display::Flex)       // flex
    .tw(FontWeight::Bold)    // font-bold

Calling .tw(Padding::X(2)) after .tw(Padding::X(4)) would either:

• Option A: Compile-time error (via typestate pattern — more complex)
• Option B: Runtime replacement of the previous value in the same category (simpler, still catches conflicts)

2. Enum-based categories

enum Padding { X(u8), Y(u8), T(u8), B(u8), L(u8), R(u8), All(u8) }
enum Margin { X(u8), Y(u8), T(u8), B(u8), L(u8), R(u8), All(u8), Auto }
enum Display { Block, Flex, Grid, Hidden, Inline, InlineBlock, ... }
enum TextAlign { Left, Center, Right, Justify }
enum FontSize { Xs, Sm, Base, Lg, Xl, ... }
// etc.

Each enum variant maps to the corresponding Tailwind class string.

3. Escape hatch for arbitrary strings

element
    .tw(Padding::X(4))
    .tw_raw("custom-class")  // raw string for non-standard classes

4. Responsive and state variants

element
    .tw(Padding::X(4))
    .tw_md(Padding::X(8))     // md:px-8
    .tw_hover(TextColor::Blue(600))  // hover:text-blue-600

Open Questions

• Should conflict detection be compile-time (typestate) or runtime (last-wins with warning)?
• How to handle Tailwind's arbitrary value syntax (px-[13px])?
• Should the crate auto-generate enums from the Tailwind config or be hand-maintained?
• Integration with the html! macro syntax?</issue_description>

Comments on the Issue (you are @copilot in this section)

@dannywillems > Integration with the html! macro syntax?

yes

How to handle Tailwind's arbitrary value syntax (px-[13px])?

yes

Should the crate auto-generate enums from the Tailwind config or be hand-maintained?

if a config exist, generate from config.

Should conflict detection be compile-time (typestate) or runtime (last-wins with warning)?

always compile time</comment_new>